Why Apollo

It works beside the systems you already run.

Keep your current systems. Apollo just reads the files you already have.

01 / Side by side

Apollo against a typical RTO platform.

ApolloA typical RTO platform
What its AI readsYour files as handed in: Word, Excel, PDF, scansAnswers typed into its own forms
Who makes the judgementYour assessorOften a suggested result, accepted in bulk
What the feedback saysQuotes the work and says what to fixOften just a result, with the wording left to you
Where student work sitsNot kept by ApolloOn their servers
Who pays for the AIIncluded in your feeBuilt into their subscription
Integrity checkingCompares the class, on your computerGenerally not offered
To adopt itSign in from a browser. Nothing to move overData migration and re-authoring assessments
What a trainer learnsOne screenA whole platform
To stop using itCancel any time. Nothing to take backYour records live in their system
02 / What we call it

Why we call it a VET Education Co-Pilot.

Built for VET, works for the trainer, and helps rather than decides.

01

VET. It reads the real evidence

Apollo reads what the learner handed in, against your marking guide.

02

Trainer. The decision stays with them

Under the Standards, the assessor decides competence. Apollo can’t.

03

Co-pilot. It does the hours in front of the decision

It does the reading and drafting, so you have more time to judge.

04

And the record says so

Each returned document shows who marked it, and when.

03 / Straight answers

What Apollo is not.

It’s a marking instrument, and deliberately nothing more than that.

Not

Not a student management system

No enrolments, no certificates, no AVETMISS reporting. Apollo works alongside whatever you already run.

Not

Not a plagiarism database

The integrity check compares the class in front of it and the sample answer. It cannot see the web or previous cohorts.

Not

Not the decision-maker

Not

Not a validation service

It gives your validators something explicit to review. It doesn’t do the validating.

04 / The numbers

How one trainer timed it, and what we haven’t proven.

Our marking-time figures come from one batch, timed by the trainer; estimates and extrapolations are labelled. Trainers’ own times are quoted as they gave them. Here’s the method, including where it falls short.

2.0hrs
to mark 24 assessments. Her estimate by hand was 6.5 hours. She timed the two hours, from download to re-upload.
5min
per assessment, against her estimate of 16.25 minutes by hand. Your own minutes will differ.
24
assessments in the timed batch.

Not yet proven: one trainer, one batch. Marking quality hasn’t been independently checked.

Read it in your own numbers.

Run one unit through Apollo and measure your own turnaround and hours against last term.